Flow Architectures: The Future of Streaming and Event-Driven Integration

Flow Architectures: The Future of Streaming and Event-Driven Integration

  • Downloads:1133
  • Type:Epub+TxT+PDF+Mobi
  • Create Date:2021-04-14 11:52:14
  • Update Date:2025-09-06
  • Status:finish
  • Author:James Urquhart
  • ISBN:1492075892
  • Environment:PC/Android/iPhone/iPad/Kindle

Summary

Software development today is embracing events and streaming data, which optimizes not only how technology interacts but also how businesses integrate with one another to meet customer needs。 This phenomenon, called flow, consists of patterns and standards that determine which activity and related data is communicated between parties over the internet。

This book explores critical implications of that evolution: What happens when events and data streams help you discover new activity sources to enhance existing businesses or drive new markets? What technologies and architectural patterns can position your company for opportunities enabled by flow? James Urquhart, global field CTO at VMware, guides enterprise architects, software developers, and product managers through the process。


Learn the benefits of flow dynamics when businesses, governments, and other institutions integrate via events and data streams
Understand the value chain for flow integration through Wardley mapping visualization and promise theory modeling
Walk through basic concepts behind today's event-driven systems marketplace
Learn how today's integration patterns will influence the real-time events flow in the future
Explore why companies should architect and build software today to take advantage of flow in coming years

Download

Reviews

Wojtek

This book contains some interesting ideas 。。。 but that's not enough。 It's overly theoretical and does not provide any value from that theoretical hand waving。 A great example is the Wardley Mapping process, which is pretty interesting as a whole (and it is a good representation of the whole mapping process) but does not have any value attached - because it's all speculation。 This book contains some interesting ideas 。。。 but that's not enough。 It's overly theoretical and does not provide any value from that theoretical hand waving。 A great example is the Wardley Mapping process, which is pretty interesting as a whole (and it is a good representation of the whole mapping process) but does not have any value attached - because it's all speculation。 。。。more

Nick

Well worth a read if you have an interest in the potential of standardised and ubiquitous ways that systems will share and consume information asynchronously and at global, distributed scale。I recommend sticking with it - the final chapter (#6) is one of the most interesting parts of the book。

Sebastian Gebski

I've reached for this book because of its author: a person with incredible knowledge and experience。Unfortunately, I can't say I liked the book, for several reasons:1。 It's over-theoreticized, and in a bad way - some considerations are really non-trivial, but it doesn't feel like they bring anything valuable in the end2。 I'm still struggling to determine who's the proper audience, it feels like Urquhart was not sure either。3。 The author reached for very interesting tools to address the flow arch I've reached for this book because of its author: a person with incredible knowledge and experience。Unfortunately, I can't say I liked the book, for several reasons:1。 It's over-theoreticized, and in a bad way - some considerations are really non-trivial, but it doesn't feel like they bring anything valuable in the end2。 I'm still struggling to determine who's the proper audience, it feels like Urquhart was not sure either。3。 The author reached for very interesting tools to address the flow architectures: the promise theory and Wardley maps。 When it comes to the former, I like the idea, but it appears over-explored (is given too much space in a repetitive way)。 And about the latter - Wardley maps are a very interesting mental model, but unfortunately with a very limited applicability (usage) IMHO - TBH I don't see much value in using them in this book。Sadly, I don't think this book has brought anything new to the table。 It feels like Urquhart had a shadow of the idea, he was not sure where writing will lead him, but he hoped it will be good。 IMHO he was wrong (with all the respect) - the same portion of raw, objective knowledge could have been delivered in 3 blog posts。 Why 3? Not because there would be too much content for 1, I'd just tailor the message to 3 separate recipient groups: non-tech, top level mgmt and tekkies。Sadly, I can't recommend this book :( 。。。more

Ben Ford

A well thought through, and convincingly argued, imagining of the next decade of technical development in real time applications。

ferhat

It's a manager book around why and future estimations, and very repetitive。 It's a manager book around why and future estimations, and very repetitive。 。。。more

Sandeep

Still waiting for the remaining chapters。。。